Coverage Report for CI Build 25996995172

Coverage remained the same at 85.297%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

Coverage Stats

Relevant Lines:	13671
Covered Lines:	11661
Line Coverage:	85.3%
Coverage Strength:	395.78 hits per line

💛 - Coveralls

concept ACK but @nothingmuch brought up out of band that dotnet-sdk_8 is considered insecure and furthermore we should set DOTNET_CLI_TELEMETRY_OPTOUT in the devshell in dotnet-sdk_10

I see, considering making dotnet-sdk_10 the default, the case for dotnet-sdk_8 was compatibility, hopefully 8 has faded out

Updated this to use SDK 10 tooling while preserving the current net8.0 runtime compatibility. The dev shell now combines dotnetCorePackages.sdk_10_0 with dotnetCorePackages.runtime_8_0, sets DOTNET_CLI_TELEMETRY_OPTOUT=1, and updates global.json to select SDK 10.

I kept the project target on net8.0 so this does not raise the runtime compatibility floor.

After some diggin into this a bit more.

BTCPay’s .NET 10 floor appears to be BTCPay Server 2.3.7: their 2.3.7 release notes say it is the first release using .NET 10, and their migration guide tells plugin authors moving to net10.0 to bump the minimum BTCPay Server requirement to >=2.3.7.

So I'm opting to have net 10 but still have net 8 compatibility